Dynamically reconfiguring data plane of forwarding element to account for power consumption

ABSTRACT

Some embodiments of the invention provide a network forwarding element that can be dynamically reconfigured to adjust its data message processing to stay within a desired operating temperature or power consumption range. In some embodiments, the network forwarding element includes (1) a data-plane forwarding circuit (“data plane”) to process data tuples associated with data messages received by the IC, and (2) a control-plane circuit (“control plane”) for configuring the data plane forwarding circuit. The data plane includes several data processing stages to process the data tuples. The data plane also includes an idle-signal injecting circuit that receives from the control plane configuration data that the control plane generates based on the IC&#39;s temperature. Based on the received configuration data, the idle-signal injecting circuit generates idle control signals for the data processing stages. Each stage that receives an idle control signal enters an idle state during which the majority of the components of that stage do not perform any operations, which reduces the power consumed and temperature generated by that stage during its idle state.

CLAIM OF BENEFIT TO PRIOR APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/870,680, filed May 8, 2020, which is a continuation of U.S. patent application Ser. No. 15/683,743, filed Aug. 22, 2017. U.S. patent application Ser. Nos. 16/870,680 and 15/683,743 claims the benefit of U.S. Provisional Patent Application 62/426,674, filed Nov. 28, 2016 and U.S. Provisional Patent Application 62/456,641, filed Feb. 8, 2017. The entire specifications of which are hereby incorporated herein by reference in their entirety.

BACKGROUND

A network forwarding chip often has to meet stringent operating temperature and power consumption requirements within a network forwarding element (e.g., a switch or a router). Meeting these requirements is often not trivial, as it requires controlling the dynamic power consumption of the network forwarding chip. This is because modern fabrication processes use advanced lithographic processes to produce semiconductor chips with very small feature sizes (e.g., smaller transistor gate lengths, etc.). The smaller feature sizes allow many high-speed components (e.g., transistors) to be defined on the chip. Most of these components consume the majority of their power during their dynamic operations (e.g., when they are changing their states). As a component's contribution to the operating temperature of the chip is related to the component's power consumption, the component's temperature contribution is primarily related to its dynamic operation.

To date, there have not been many good solutions for controlling the operating temperature and power consumption of network forwarding chips. Therefore, there is a need in the art for novel techniques that can control the operating temperature and power consumption of network forwarding chips.

SUMMARY

Some embodiments of the invention provide a network forwarding data plane circuit (“data plane”) that can be dynamically reconfigured to adjust its data message processing to stay below a maximum operating temperature. Instead of or in conjunction with this capability, the data plane of some embodiments can be dynamically reconfigured to adjust its data message processing to stay below a desired power consumption level. Also, in some embodiments, the data plane can be dynamically reconfigured to increase its data message processing for a transient period of time in order to alleviate congestion in its message storing queues.

In some embodiments, the data-plane forwarding circuit (“data plane”) is implemented as an application specific integrated circuit (ASIC). Also, in some embodiments, the data plane process data tuples associated with data messages received by the data plane. Typically, the data-plane forwarding circuit is part of a network forwarding element (e.g., a switch, a router, etc.) that includes a control-plane circuit (“control plane”) that configures the data-plane forwarding circuit. The data plane includes several data processing stages to process the data tuples. The operations of these processing stages are typically configured by the control plane.

The data plane also includes an idle-signal injecting circuit that receives from the control plane configuration data that the control plane generates based on the data plane's operating temperature. Based on the received configuration data, the idle-signal injecting circuit generates idle control signals for the data processing stages. Each stage that receives an idle control signal enters an idle state during which the majority of the components of that stage do not perform any operations, which reduces the power consumed and temperature generated by that stage during its idle state.

The data-plane forwarding circuit in some embodiments has a set of one or more temperature sensors that detect the temperature of the data-plane forwarding circuit and report this detected temperature to the control plane. In some embodiments, the temperature sensor set includes one or more thermal diodes, each of which outputs a current that is based on the junction temperature on the data-plane forwarding IC's die. The temperature sensor includes a converter circuit that converts the current output by the thermal diode(s) to a value that is associated with the operating temperature of the IC. This value is then provided to the control plane, which then uses this value to identify the operating temperature of the IC.

In some embodiments, the idle-signal injecting circuit is part of a parsing circuit that (1) parses the headers of the data messages (e.g., the packets) that the data-plane forwarding circuit receives, and (2) generates a set of data tuples for each received data message for the data plane's data processing stages to process. Each data tuple set is referred to below as a header vector. In some embodiments, the parser extracts a data message's payload and passes this payload along another path (that does not traverse through the data plane's data processing stages) to a deparser that combined the payload with the message's processed header vector to reconstitute the data message. In some embodiments, the header vector only includes L4, L3 and/or L2 header values, while in other embodiments, the header vector also includes higher layer parameters, such as L7 parameters.

In some embodiments, the parsing circuit includes several parsers, with each parser processing data messages that it receives (e.g., processing data messages received at one of the physical input interfaces of the data-plane forwarding circuit). These parsers provide the header vectors that they generate to an arbitration circuit of the parsing circuit. The arbitration circuit has (1) a set of queues for storing these header vectors, and (2) a data fetcher for retrieving header vectors from the set of queues and passing them through the data processing stages of the data plane.

In some embodiments, each header vector sequentially passes through several data processing stages including a set of ingress data processing stages and a set of egress data processing stages that respectively are before and after a traffic manager of the data plane. The traffic manager includes (1) queues that store the data messages (including their associated header vectors) and (2) a switching fabric that acts as a crossbar switch for directing data messages from different ingress pipelines to different egress processing pipelines. In some embodiments, the different pipelines are associated with different ports of the data-plane forwarding circuit. By directing the data messages between different ingress and egress pipelines that are associated with different ports, the traffic manager's switching fabric in these embodiments performs the forwarding operation of the forwarding element by directing data messages between the input and output ports of the data-plane forwarding circuit.

The idle-signal injecting circuit is part of the data fetcher of the arbitration circuit in some embodiments. Based on configuration data received from the control plane and stored in a storage (e.g., a register) accessible to the data fetcher, the data fetcher generates idle control signals at a particular rate (e.g., an idle control signal for each set of N header vectors transmitted, or transmitted every M microseconds), and sends these signals as header vectors through the data processing stages of the data plane. Like the other header vectors, each idle-signal header vector sequentially passes through several data processing stages.

In some embodiments, each idle-signal header vector has only a subset of bits that matter, and all its other bits (even if defined) are irrelevant. For instance, in some embodiments, the idle-signal header vector has only one bit that matters, a valid bit. This valid bit controls a set of clock gating circuits for each data processing stage that receives this valid bit. When this valid bit is inactive (e.g., it has a low value), a clock gating circuit set of a data processing stage that receives this valid bit will not clock (i.e. will maintain the clock signal inactive for) a set of input storage units (e.g., a set of flip-flops) that receive and maintain that stage's input values. In other embodiments, the idle control signals are signals that are transmitted through the data processing stages of the data plane separately from the header vectors.

By preventing these input storage units from receiving the active clock signal, these storage units do not change the values that they store (i.e., do not change state). By not changing their state and remaining idle, these input storage units consume less power, which over a sufficient number of idle cycles for a sufficient number of stages reduces the temperature of the data-plane forwarding circuit. Maintaining the inputs of a data processing stage constant during two or more successive clock cycles prevents that stage's processing modules (e.g., its match action units, memories, logic units, etc.) from performing new operations in one or more of the successive clock cycles, which further reduces the dynamic power consumption of the data-plane forwarding circuit and thereby further allows the data-plane forwarding circuit to cool.

Instead of, or in conjunction with, injecting idle signals to control temperature, some embodiments inject idle signals to control power consumption of the data-plane forwarding circuit. For instance, the data-plane forwarding circuit of some embodiments is used by a network forwarding element that has a power regulator that identifies the power consumed by the forwarding element and/or by the data-plane forwarding circuit. In some embodiments, the power regulator is an on-chip regulator that is implemented on the data-plane forwarding circuit. In other embodiments, the power regulator is not on the data-plane forwarding circuit (i.e., the regulator is part of the network forwarding element, but not the data-plane forwarding circuit).

When the consumed power exceeds or nears a particular threshold value, the power regulator generates a signal that is supplied to the control plane directly or indirectly (e.g., through another component of the forwarding element that generates a signal to the control plane in response to the signal from the power regulator). In response to this signal, the control plane dynamically reconfigures the idle-signal injecting circuit to increase the number of idle signals it generates, in order to reduce the power consumption of the data-plane forwarding circuit.

As mentioned above, the idle signals in some embodiments prevent the input storage units of the data processing stages from receiving the active clock signal, which prevents these storage units from changing their values (i.e., prevents them from changing state), and thereby allows them to consume less power. This power saving can be significant because the vast majority of power consumption of a typical data plane today is its dynamic power consumption (as opposed to its static power consumption).

Also, as mentioned above, maintaining the inputs of a data processing stage constant during two or more successive clock cycles causes that stage's processing modules (e.g., its match action units, memories, logic units, etc.) from performing new operations in one or more of the successive clock cycles, which further reduces the dynamic power consumption of the data-plane forwarding circuit. Examples of operations that the stage's processing modules will not perform include instruction or data lookup operations, data write operations, arithmetic operations, etc.

Instead of increasing the number or frequency of the idle signals to reduce the data plane's operating temperature or power consumption, some embodiments dynamically reconfigure the idle-signal injecting circuit of the data plane to reduce the number of idle signals it generates, in order to increase the data message processing of the data-plane forwarding circuit for a transient period of time. For example, in some embodiments, the data-plane forwarding circuit is designed for a first data throughput rate, but it can, for a time period, increase its data message processing throughput to reach a higher second data throughput rate in order to alleviate the build up of data messages in one or more queues in the data plane. In these embodiments, the control plane has a set of one or more monitoring processes that detect when a set of one or more queues in the data plane have exceeded a particular depth. In response to this detection, the control plane reconfigures the idle-signal generator(s) of the data plane to reduce the number or frequency of the generated idle signals in order to increase the data plane's data message processing throughput for a transient period of time.

In some embodiments, the data-plane forwarding circuit is configured by a set of design automation software tools that allow the data-plane forwarding circuit to custom select any subset of R features, from a set of S available features that can be implemented by the data-plane forwarding circuit (where R and S are integers and R is equal to or less than S), in order to stay within a desired power consumption level. Accordingly, the same manufacturer, or different manufacturers, of network forwarding elements that deploy the data-plane forwarding circuits of some embodiments can differently configure two identical data-plane forwarding circuits to implement two different subsets of features to operate within two different power consumption levels. The two data-plane circuits are configured to operate with two different power consumption levels in some embodiments by having their idle signal generators pass idle signals through the data plane circuits at two different rates (i.e., two different frequencies).

The preceding Summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this document. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description and the Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description and the Drawings, but rather are to be defined by the appended claims, because the claimed subject matters can be embodied in other specific forms without departing from the spirit of the subject matters.

BRIEF DESCRIPTION OF FIGURES

The novel features of the invention are set forth in the appended claims. However, for purposes of explanation, several embodiments of the invention are set forth in the following figures.

FIG. 1 illustrates an example of a network forwarding element of some embodiments.

FIG. 2 illustrates a process that the network forwarding elements performs in some embodiments to increase the rate of idle signal generation in order to decrease the operating temperature of its data-plane forwarding circuit.

FIG. 3 illustrates a network forwarding element of some embodiments that injects idle signals through the data plane to control its power consumption.

FIG. 4 illustrates a process that the network forwarding element of FIG. 3 performs in some embodiments.

FIG. 5 illustrates a process that the network forwarding element performs in some embodiments to reconfigure its data plane to increase the data plane's data message processing throughput for transient periods of time.

FIG. 6 illustrates that the data plane in some embodiments include counters for the data plane queues.

FIG. 7 illustrates the circuitry for placing a data processing stage in an idle state in response to an idle signal.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerous details, examples, and embodiments of the invention are set forth and described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention may be practiced without some of the specific details and examples discussed.

Some embodiments of the invention provide a network forwarding data plane circuit (“data plane”) that can be dynamically reconfigured to adjust its data message processing to stay below a maximum operating temperature. Instead of or in conjunction with this capability, the data plane of some embodiments can be dynamically reconfigured to adjust its data message processing to stay below a desired power consumption level. Also, in some embodiments, the data plane can be dynamically reconfigured to increase its data message processing for a transient period of time in order to alleviate congestion in its message storing queues.

In some embodiments, the data-plane forwarding circuit (“data plane”) is implemented as an application specific integrated circuit (ASIC). Also, in some embodiments, the data plane process data tuples associated with data messages received by the data plane. Typically, the data-plane forwarding circuit is part of a network forwarding element (e.g., a switch, a router, etc.) that includes a control-plane circuit (“control plane”) that configures the data-plane forwarding circuit. The data plane includes several data processing stages to process the data tuples. The operations of these processing stages are typically configured by the control plane.

The data plane also includes an idle-signal injecting circuit that receives from the control plane configuration data that the control plane generates based on the data plane's operating temperature. Based on the received configuration data, the idle-signal injecting circuit generates idle control signals for the data processing stages. Each stage that receives an idle control signal enters an idle state during which the majority of the components of that stage do not perform any operations, which reduces the power consumed and temperature generated by that stage during its idle state.

The data-plane forwarding circuit in some embodiments has a set of one or more temperature sensors that detect the temperature of the data-plane forwarding circuit and report this detected temperature to the control plane. In some embodiments, the temperature sensor set includes one or more thermal diodes, each of which outputs a current that is based on the junction temperature on the data-plane forwarding IC's die. The temperature sensor includes a converter circuit that converts the current output by the thermal diode(s) to a value that is associated with the operating temperature of the IC. This value is then provided to the control plane, which then uses this value to identify the operating temperature of the IC.

FIG. 1 illustrates an example of a network forwarding element of some embodiments that has a data plane that can be dynamically reconfigured to adjust its data message processing to stay below a maximum operating temperature. The network forwarding element 100 is a standalone network forwarding element (e.g., a standalone network switch or router) in some embodiments, while it is a forwarding element that is part of a computer (e.g., is incorporated in a network interface card of a computer) in other embodiments.

As shown, the network forwarding element 100 includes a data-plane forwarding circuit 105, a control-plane circuit 110, and a set of one or more temperature sensors 115. In some embodiments, the data-plane forwarding circuit 105 and the control-plane circuit 110 are on different IC dies that are packaged on different IC chips. In other embodiments, these two circuits are on different IC dies that are packaged within the same IC chip. In still other embodiments, these two circuits are on the same IC die that is packaged on the same IC chip.

The data plane circuit 105 is the forwarding IC in some embodiments that is used by the network forwarding element 100 to perform the forwarding operations that determine how the forwarding element should forward received data messages to the data message destinations (e.g., to computers connected to the electronic device) or to other network forwarding elements. As shown, the data-plane forwarding circuit 105 includes several parallel ingress pipelines 120, several parallel egress pipelines 122, and a traffic manager 124. Each of the pipelines 120 and 122 includes a parsing circuit 130, multiple data processing stages 135, and a de-parsing circuit 140.

A temperature sensor 115 detects the temperature of the IC and reports this detected temperature to the control-plane circuit 110 (“control plane”). In some embodiments, each temperature sensor includes one or more thermal diodes that sense the junction temperature on the IC die of the data plane forwarding circuit. A thermal diode in some embodiments outputs a current that is based on the junction temperature on the IC die. In some embodiments, the temperature sensor includes a converter circuit that converts the current output by the thermal diode(s) to a value that is associated with the operating temperature of the IC. This value is then provided to the control plane, which then uses this value to identify the operating temperature of the data-plane forwarding circuit.

The control plane 110 configures the data plane forwarding circuit 105 (“data plane”). In some embodiments, the control plane includes one or more processors 192 that execute instructions and a memory 194 that stores instructions. In some embodiments, each processor 192 is a microprocessor with multiple processing cores or units. Examples of such a microprocessor include any off-the-shelf processors commonly available today. In contrast to such off-the-shelf microprocessor, the data-plane forwarding circuit 105 is an application specific IC (ASIC) in some embodiments.

The instructions for the processor(s) 192 can be specified by (1) a manufacturer of the network forwarding element 100, (2) a network administrator that deploys and maintains the network forwarding element 100, or (3) one or more automated processes that execute on servers and/or network forwarding elements that monitor network conditions. A processor 192, or another circuit of the control plane, communicates with the data plane (e.g., to configure the data plane or to receive statistics from the data plane) through a data plane interface (e.g., a peripheral device interface, such as a PCIe interface).

In some embodiments, the data plane 105 processes data tuples associated with data messages received by the forwarding element, in order to forward the data messages to their destinations or their next hops. Specifically, the data plane 105 processes data tuples (e.g., message headers) associated with the received data messages in order to forward the data messages to destination devices connected to the forwarding element or to other forwarding elements in a network that serve as the next hops in the network for the data messages. In some embodiments, the data plane's processing stages process the data tuple processes data tuples to forward the data messages to destination devices or to other forwarding elements in the network, by comparing the data tuples with flow-entries that the control-plane circuit provides the data-plane forwarding circuit. Examples of such flow-entries include ACL flow-match entries that are stored in one or more match-action tables of the data processing stages.

As further described below, the data plane includes at least one idle-signal injecting circuit 188 that (1) receives from the control plane configuration data that the control plane generates based on the data plane's temperature, and (2) based on the received configuration data, generates idle control signals for the data processing stages of the data plane. Some embodiments only have idle-signal injecting circuits 188 in the parallel ingress pipelines 122 (e.g., in the parsing circuit 130 of each ingress pipeline 120). Other embodiments have an idle-signal injecting circuit 188 in each ingress or egress pipeline 120 or 122 (e.g., in the parsing circuit 130 of each ingress or egress pipeline 120 or 122). Each stage that receives an idle control signal enters an idle state during which all or a majority of the components of that stage do not perform any operations, which reduces the power consumed and temperature generated by that stage during its idle state.

When the data-plane forwarding circuit receives a data message, the message in some embodiments is directed to an ingress pipeline 120. In some embodiments, different ingress and egress pipelines are associated with different physical ports of the data-plane forwarding circuit 105. In some embodiments, the parsing circuit 130 of the ingress pipeline 120 that receives a data message (1) parses the headers of the data messages (e.g., the packets), and (2) generates a set of data tuples for each received data message for the data plane's data processing stages to process. Each data tuple set is referred to below as a header vector, as typically the parsing circuit separates a data message's header from its payload, defines a header vector from the header, and passes the payload along another path 160 (that does not traverse through the ingress pipeline's data processing stages 135) to the de-parser 140 of the ingress pipeline. The structure of the parsing circuit 130 will be further described below.

The parsing circuit 130 of the ingress pipeline passes each header vector that it generates to the first data processing stage 135. In some embodiments, each header vector then sequentially passes through each of the data processing stages 135 of the ingress pipeline until it reaches the de-parser 140 of this pipeline. In some embodiments, each data processing stage includes a storage unit 170 and a match-action-unit (MAU) 175. For each clock cycle, the storage unit 170 receives the input to the MAU 175, and holds this input constant while the MAU 175 performs its operation, unless the storage unit receives an idle signal. The storage unit 170 includes a set of flip-flops in some embodiments. When the storage unit 170 for a data processing stage receives an idle signal, it does not change its state (i.e., does not receive new input), which prevents it from consuming power for a state change and prevents it from supplying new input for the MAU to process. This will be further described below.

Each stage's MAU 175 searches one or more tables to identify records that match a header vector (i.e., to perform lookups based on the header vectors) and performs actions based on the matching records (i.e., performs actions based on the lookups). In some embodiments, an MAU includes a sequence of stages, with each stage including one or more match tables and an action engine. Each match table includes a set of match entries against which the header fields are matched (e.g., using hash tables), with the match entries referencing action entries. When the header vector matches a particular match entry, that particular match entry references a particular action entry that specifies a set of actions to perform on the header vector (e.g., sending the data message to a particular port, modifying one or more header field values, dropping the data message, mirroring the data message to a mirror buffer, etc.). The action engine of the stage performs the actions on the header vector, which is then sent to the next stage of the MAU.

The de-parser 140 reconstructs the data message using the header vector received from the last data processing stage 135 (as modified by the data processing stages 135) and the payload received directly from the parsing circuit 130. In some embodiments, the de-parser constructs a data message that can be sent out onto the wire. The de-parser of the ingress pipeline provides the data message that it reconstructs to the traffic manager 124.

After passing through the selected ingress pipeline 120, a data message arrives at the traffic manager 124. The traffic manager includes queues that store the data messages (including their associated header vectors) and the data plane's switching fabric that acts as a crossbar switch that dispatches the data message to one of the egress pipelines 122. The traffic manager's switching fabric allows this manager 124 to direct a data message that is received along an ingress pipeline associated with a physical port that received the data message, to an egress pipeline associated with the same or different physical port that needs to transmit the data message.

Once the traffic manager dispatches the data message to an egress pipeline 122, the data message is processed in the same fashion as described above for the ingress pipeline 120. In other words, the egress pipeline's parsing circuit extracts a header vector from the data message, passes this header vector to the data processing stages 135 of its pipeline, and passes the data message's payload to the pipelines de-parser 140. The data processing stages sequentially process the header vector and provide this header vector to the de-parser to reconstitute the data message (when the message does not get dropped) to transmit along one of the physical ports. In general, a typical data message will be processed once by an ingress pipeline, the traffic manager, and an egress pipeline.

As mentioned above, the control plane 110 reconfigures the data plane's idle-signal injecting circuit 188 whenever a temperature sensor detects that the data plane's temperature has passed a threshold, so that this circuit 188 can inject idle signals into the data processing pipeline to reduce the temperature of the data plane. As shown, the idle-signal injecting circuit is part of a parsing circuit 130. The parsing circuit 130 includes several parsers 180, with each parser processing data messages that it receives (e.g., processing data messages received at one of the physical input interfaces of the data plane forwarding circuit).

Each parser, in some embodiments, receives a data message as a formatted collection of bits in a particular order, and parses the message into its constituent header fields according to a parse graph state machine. That is, the parser starts from the beginning of the message and parses each header field in order, assigning these header fields to fields of a message header vector for processing. Based on the values of certain fields (e.g., the Ethertype field of an Ethernet header, the Protocol field of an Internet Protocol header, etc.), the parser can determine the structure of the next set of header fields. In some embodiments, each parser 180 separates out the message headers (up to a designated point) from the payload of the message, and sends the payload directly to the de-parser 140 through path 160 without going through the MAU processing stages. In other embodiments, while sending the payload directly to the de-parser 140, the parser 180 also sends passes some or all part of the payload through the MAU processing stages.

The parsers 180 provide the header vectors that they generate to an arbitration circuit 182 of the parsing circuit 130. The arbitration circuit has (1) a set of queues 184 for storing these header vectors, and (2) a data fetcher 186 for retrieving header vectors from the set of queues 184 and passing them through the data processing stages of the data plane based on the priorities of the data messages and/or queues.

As shown, the idle-signal injecting circuit 188 is part of the data fetcher 186 of the arbitration circuit in some embodiments. Based on configuration data received from the control plane and stored in a configuration storage 190 (e.g., a register) accessible to the data fetcher, the data fetcher generates idle control signals at a particular rate (e.g., an idle control signal for each set of N header vectors transmitted, or each set of N header vectors transmitted every M microseconds), and sends these signals as header vectors through the data processing stages of the data plane. Like the other header vectors, each idle-signal header vector sequentially passes through several data processing stages.

In some embodiments, each idle-signal header vector has only a subset of bits that matter, and all of its other bits (even if defined) are irrelevant. For instance, in some embodiments, the idle-signal header vector has only one bit that matters, a valid bit. This valid bit controls a set of clock gating circuits that control the clock signal that is supplied to the storage units 170 of each data processing stage 135 that receives this valid bit. When this valid bit is inactive (e.g., it has a low value), a clock gating circuit set of a data processing stage 135 that receives this valid bit will not clock (i.e. will maintain the clock signal inactive for) the storage units 170 that receive and maintain this stage's input values for the MAU 175 of this stage. The clock gating circuit of some embodiments will be further described below by reference to FIG. 7.

By preventing the storage unit 170 of a stage 135 from receiving the active clock signal, the active idle bit prevents the storage unit 170 from changing the values that it stores (i.e., does not change state). By not changing its state and remaining idle, the storage unit consumes less power, which over a sufficient number of idle cycles for a sufficient number of stages reduces the temperature of the IC. Maintaining the inputs of a data processing stage constant during two or more successive clock cycles prevents that stage's MAU 175 (including its match engine, action engine, memories, logic units, etc.) from performing new operations in one or more of the successive clock cycles, which further reduces the dynamic power consumption of the IC and thereby further allows the IC to cool.

FIG. 2 illustrates a process 200 that the network forwarding element performs in some embodiments to increase the rate of idle signal generation of the data plane in order to decrease the operating temperature of the data-plane forwarding circuit. The first three operations of the process 200 are performed by the control plane 110, while the fourth operation of this process is performed by the data plane 105. As shown, the control plane initially detects (at 205) that the operating temperature of the data plane has exceeded a particular temperature value.

In some embodiments, the control plane detects this condition when it receives a signal from an on-chip temperature sensor 115 of the data plane 105 that the junction temperature of the data plane IC has exceeded the particular temperature value. In some embodiments, this particular temperature value is a threshold value that is lower than a maximum acceptable operating temperature of the data plane IC. This lower threshold value is selected in these embodiments in order to ensure that the data plane has sufficient time to increase its idle signal generation in order to cool off. In some embodiments, the control plane performs the process 200 for different detected data plane operating temperatures, in order to reconfigure the data plane's operation differently for different detected operating temperatures.

After detecting that the data plane's operating temperature has exceeded the particular temperature value, the control plane generates (at 210) new configuration data to reconfigure the idle signal generator(s) 188 of the data plane 105. In some embodiments, the control plane has a lookup table that stored different configuration data sets (that specify different rates of idle signal generation) for different detected data plane operating temperatures. The control plane in these embodiments identifies the configuration data set to supply to the data plane by using the detected temperature to identify the record in the lookup table that specifies the configuration data set.

At 215, the control plane supplies the generated configuration data set to the data plane 105 for storage in the configuration data store(s) 190 of the idle signal generator(s) 188. Next, at 220, the data plane starts to generate idle signals at the rate specified by the new configuration data set stored in the configuration data store(s) 190. As mentioned above, an idle signal generator 188 of the data fetcher 186 of the parsing circuit's arbitration unit retrieves the configuration data set from the configuration data store 190, and generates the idle signals at a rate specified by the configuration data set. The generated idle signals, in turn, reduce the power consumption of the data processing stage 135 and the de-parser 140, and thereby reduce the operating temperature of the data plane forwarding circuit. After 220, the process 200 ends.

Instead of, or in conjunction with, injecting idle signals to control temperature, the network forwarding element of some embodiments injects idle signals through the data plane to control the data plane's power consumption. FIG. 3 illustrates one such a network forwarding element. This network forwarding element 300 is similar to the network forwarding element 100 of FIG. 1, except that its control plane 110 reconfigures its data plane 105 in response to a signal from a power regulator 315. Based on the signal from the power regulator 315, the control plane 110 determines that the data plane, or the forwarding element that uses the data plane, has exceeded a threshold.

The power regulator 315 identifies the power consumed by the forwarding element and/or by the data plane forwarding circuit. For the embodiments illustrated by FIG. 3, the power regulator 315 is not part of the data plane forwarding circuit. Instead, it is an off-chip power regulator that is part of the network forwarding element. In other embodiments, the power regulator is an on-chip regulator that is implemented on the data plane forwarding circuit.

When the consumed power exceeds or nears a particular threshold value, the power regulator generates a signal that is supplied to the control plane 110 directly or indirectly (e.g., through another component of the forwarding element that generates a signal to the control plane in response to the signal from the power regulator). In response to this signal, the control plane 110 dynamically reconfigures idle-signal generators 188 in the data plane to increase the number of idle signals it generates in order to reduce the data plane's power consumption. As described above, the control plane 110 reconfigures these generators by writing new configuration data to the configuration data storages 190 accessed by the idle signal generators 188.

Based on the configuration data in these storages 190, the idle signal generators 188 generates idles signals, which the data fetchers 186 pass through the ingress or egress pipelines 122 or 124. The idle signals in some embodiments prevent the input storage units of the data processing stages from receiving the active clock signal, which prevents these storage units from changing their values (i.e., prevents them from changing state), and thereby allows them to consume less power. This power saving can be significant because the vast majority of the power consumption of a typical data plane forwarding circuit today is its dynamic power consumption (as opposed to its static power consumption).

Also, as mentioned above, maintaining the inputs of a data processing stage constant during two or more successive clock cycles causes that stage's processing modules (e.g., its match action units, memories, logic units, etc.) from performing new operations in one or more of the successive clock cycles, which further reduces the dynamic power consumption of the data plane forwarding circuit. Examples of operations that the stage's processing modules will not perform include instruction or data lookup operations, data write operations, arithmetic operations, etc.

FIG. 4 illustrates a process 400 that the network forwarding element 300 performs in some embodiments to increase the rate of idle signal generation in order to decrease the power consumption of its data plane forwarding circuit. The first three operations of the process 400 are performed by the control plane 110, while the fourth operation of this process is performed by the data plane 105. As shown, the control plane initially detects (at 405) that the power consumption of the forwarding element or data plane forwarding circuit has exceeded a particular power level.

In some embodiments, the control plane detects this condition when it receives a signal from the power regulator 315 that indicates that the power consumption of the forwarding element or data plane forwarding circuit has exceeded the particular power level. In some embodiments, this particular power level is a threshold value that is lower than a maximum acceptable power consumption of the forwarding element or data plane forwarding circuit. This lower threshold value is selected in these embodiments in order to ensure that the data plane forwarding circuit has sufficient time to increase its idle signal generation in order to reduce the monitored power consumption to the desired level. In some embodiments, the control plane performs the process 400 for different detected power consumptions, in order to reconfigure the data plane forwarding circuit's operation differently for different detected power consumptions.

After detecting (at 405) that the power consumption has exceeded the particular power level, the control plane generates (at 410) new configuration data to reconfigure the idle signal generator(s) 188 of the data plane 105. In some embodiments, the control plane has a lookup table that stores different configuration data sets (that specify different rates of idle signal generation) for different detected power consumptions the forwarding element or data plane forwarding circuit. The control plane in these embodiments identifies the configuration data set to supply to the data plane by using the detected power consumption to identify the record in the lookup table that specifies the configuration data set.

At 415, the control plane supplies the generated configuration data set to the data plane 105 for storage in the configuration data store(s) 190 of the idle signal generator(s) 188. Next, at 420, the data plane starts to generate idle signals at the rate specified by the new configuration data set stored in the configuration data store(s) 190. As mentioned above, an idle signal generator 188 of the data fetcher 186 of the parsing circuit's arbitration unit retrieves the configuration data set from the configuration data store 190, and generates the idle signals at a rate specified by the configuration data set. The generated idle signals, in turn, reduce the power consumption of the data processing stage 135 and the de-parser 140, and thereby reduce the power consumption of the data plane forwarding IC. After 420, the process 400 ends.

Instead of increasing the number or frequency of the idle signals to reduce the data plane's operating temperature or power consumption, some embodiments dynamically reconfigure idle signal injecting circuit of the data plane to reduce the number of idle signals it generates, in order to increase the data message processing of the data plane for a transient period of time. FIG. 5 illustrates a process 500 that the network forwarding element performs in some embodiments to reconfigure its data plane to increase the data plane's data message processing throughput for transient periods of time. In this process, the data plane circuit is designed for a first data throughput rate, but it can for a time period increase its data message processing throughput to reach a higher second data throughput rate in order to alleviate the buildup of data messages in one or more queues in the data plane.

The process 500 starts when the data plane forwarding IC is designed for use in a particular network forwarding element. For different deployments in different network forwarding elements, a set of design tools can design different data plane forwarding ICs that are identical (i.e., are manufactured based on the same chip architecture and fabrication process) to meet different operating temperature and/or power consumption requirements. In some embodiments, one of the operations of the design tools is to define a first set of configuration data that specify the number or frequency of idle signals that the idle-signal generators 188 generate in the data pipeline during steady state operations.

At the start of the process 500, the control plane 110 receives (at 505), from the design tool set, instructions that specify the first configuration data set. The first configuration data set is for programming the idle-signal generators 188 to produce a particular number or frequency of idle signals while the data plane 105 operates under steady state conditions (e.g., while the queues of the data plane are not congested).

At 505, the control plane 110 also receives instructions that specify one or more other sets of configuration data that are for programming the idle-signal generators 188 to produce one or more different rates of idle signals during one or more higher throughput, transient periods. Some embodiments that specify different alternative configuration data sets use these different sets in order to provide multiple different types of data message throughput adjustments for different levels of queue congestions. Other embodiments just provide one alternative configuration data set for just one type of data message throughput adjustment when the data plane's queues are congested.

At 510, the control plane 110 configures the data plane's idle-signal generators 188 by writing the first configuration data set (for the data plane's steady state operations) into one or more sets of data plane storages through the data plane interface 196. In some embodiments, these data plane storages are the configuration data storages 190 accessed by the idle-signal generators 188. In other embodiments, the control plane writes the first configuration data set in data plane storages from where other data plane circuits retrieve the configuration data and store this configuration in the configuration data storages 190.

In some embodiments, the control plane has a set of one or more monitors that detect when a set of one or more queues have exceeded a particular depth. For instance, as shown in FIG. 6, the data plane in some embodiments includes counters 605 for the data plane queues 610 before the parsers 180 of the ingress pipelines 120. These counters maintain in a counter data storage 615 a count of the number of data messages stored at any given time in the queues for processing. In some embodiments, the counter data storage 615 is a set of registers, with each register in the set storing the count of one of the counters. At any given time, the count maintained by a counter indicates the current depth of (i.e., the current number of data messages awaiting processing in) the counter's associated queue 610. When this depth (i.e., when the count) exceeds a particular number, the counter's queue is deemed to have exceeded a particular acceptable threshold value.

In some embodiments, the control plane periodically accesses through the data plane interface 196 the counter data storage 615 to retrieve the count values of the counters. When the retrieved count values exceed a particular level, the control plane 110 detects (at 515) a condition that necessitates higher throughput, data message processing through the data plane to alleviate the buildup of data messages in the data plane. In some embodiments, the control plane can detect other conditions that necessitate higher throughput, data message processing through the data plane.

In response to the detected condition, the control plane 110 supplies (at 520) the idle-signal generators 188 with a new configuration data set in order to configure these idle-signal generators to reduce the number and/or frequency of their generated idle signals, which, in turn, allows the data fetchers 186 to push through the queued-up data messages through the data processing stages 135 at a faster rate. As mentioned above, the control plane 110 supplies the configuration data set either by writing the configuration data directly to the configuration data storages 190, or by storing this data in storages from which the data can be retrieved and stored in the configuration data storages 190. In some embodiments, the control plane 110 provides different configuration data sets based on different detected queue depths, e.g., provides a second configuration data set that configures the idle signal generators to reduce the idle signals to a first level when a queue depth has exceeded a first threshold value, or provides a third configuration data set that configures the idle signal generators to reduce the idle signals to a second level when the queue depth has exceeded a second threshold value.

The process 500 then transitions to 525, where it remains until the control plane determines that it should end higher throughput data message processing. In some embodiments, the control plane determines (at 525) that it should end higher throughput data plane message processing when it determines that the queue depth counts (stored in the count data storage 615) of the counters 605 has fallen below the threshold value. To make this determination, the control plane repeatedly retrieves count values stored in the count data storage 615 after reconfiguring the data plane to operate in a higher throughput state.

Also, in some embodiments, the data plane can only operate in the higher throughput state for relatively short transient periods, because it is designed to operate usually in its steady state. Accordingly, a period of time after configuring the data plane for higher throughput operations, the control plane in these embodiments ends (at 525) the higher throughput data processing of the data plane, and reconfigures the data plane for steady state operations by directly or indirectly writing the first configuration data set in the configuration data storages 190. To reconfigure the data plane, the process 500 returns back to 510, where the control plane provides first set of configuration data to the data plane's idle-signal generators 188 to configure them to go back to their steady state operations. After returning to 510, the process 500 transitions to 515 and waits there until the next time that it detects operating conditions necessitating higher-throughput data message processing.

In the example illustrated in FIG. 5, the process 500 reconfigures the data plane to operate at one higher throughput level before reconfiguring it to operate back at its steady state level. In other embodiments, however, the control plane can sequentially reconfigure the data plane's idle-signal generators with different configuration data sets that configure these generators to produce different reduced levels of idle signals. This approach allows the control plane to gradually try different higher levels of data plane data processing throughput in order to determine whether one of the lower throughput levels can alleviate the queue congestion.

In some embodiments, the data plane forwarding IC is configured by a set of design automation software tools that allows the data plane forwarding IC to custom select any subset of R features, from a set of S available features that can be implemented by the network forwarding IC (where R and S are integers and R is equal to or less than S), in order to stay within a desired power consumption level. Accordingly, the same manufacturer, or different manufacturers, of network forwarding elements that deploy the data plane forwarding ICs of some embodiments can differently configure two identical data plane forwarding ICs to implement two different subsets of features to operate within two different power consumption levels.

FIG. 7 illustrates the circuitry for placing a data processing stage in an idle state in response to an idle signal. As mentioned above, the idle signal in some embodiments is in the form of a header vector in which only one bit matters, a valid bit. Also, as mentioned above, each processing stage includes a set of storages 170 and a set of processing units 175. The storage set 170 includes a set of flips flops, which includes a valid bit flip-flop 702 and data flip-flops 704. The valid bit flip-flop 702 is clocked differently than the data flip-flops 704. Each valid bit register is clocked by a clock signal CLK produced by a clock signal generator 705, while the data flip-flops are clocked by a clock signal CLK′ produced by a clock gating circuit 710, which generates this clock signal CLK′ from the clock signal CLK, as further described below.

The valid bit controls the clock gating circuit for the data processing stage that receives this bit. When this valid bit is inactive (e.g., it has a low value) for a stage, the clock gating circuit 710 for that stage will not clock (i.e. will maintain the clock signal inactive for) the data flip-flops 704. This prevents the data flips flops 704 for that stage from changing the values that they store (i.e., from changing state). By not changing their state and remaining idle, the data flip flops for a stage that receives an inactive valid bit consumes less power, which over a sufficient number of idle cycles for a sufficient number of stages reduces the power consumption of the data plane and reduces the temperature of the data plane. Maintaining the inputs of a data processing stage constant during two or more successive clock cycles prevents that stage's processing units 175 from performing new operations in one or more of the successive clock cycles, which further reduces the dynamic power consumption of the data plane and thereby further allows the data plane to cool.

As shown in FIG. 7, the clock gating circuit 710 includes an AND gate 720 and a latch 722. The latch 722 for a clock gating circuit of any stage N receives the valid bit from the valid bit flip flop 702 of the prior stage N−1. This latch is clocked by the inverse of the clock signal CLK (also called clock bar). This allows the latch to store the previous stage's valid bit before the rising edge of clock signal CLK. This ensures that when the clock signal CLK is active (i.e., this signal is at its rising edge), the AND gate 720 has the valid bit from the previous stage at its other input. If the valid bit is active (e.g., it has a high value), the AND gate 720 outputs an active clock signal CLK′ when the clock signal CLK rises. This enables the data flip flops of stage N to receive and store the header vector (HV) data output from the processing units 175 of stage N−1. On the other hand, when the valid bit is inactive (e.g., it has a low value), the AND gate 720 outputs an inactive clock signal CLK′ and this prevents the data flip flops 704 from changing state.

While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. Accordingly, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims. 

1. A network interface device comprising: a first stage of a packet processing pipeline and a second stage of the packet processing pipeline, wherein power consumed by the first or second stage of the packet processing pipeline is to be reduced by placing the first or second stage in an idle state.
 2. The network interface device of claim 1, comprising a data-plane forwarding circuit and a control plane circuit.
 3. The network interface device of claim 1, comprising a power detecting circuit that identifies power consumption of the data-plane forwarding circuit.
 4. The network interface device of claim 1, wherein a configuration data specifies the frequency at which the idle-signal injecting circuit generates idle signals.
 5. The network interface device of claim 1, wherein an idle signal traverses successively through several data processing stages.
 6. The network interface device of claim 5, comprising: a parsing circuit for generating data tuples from the received data messages and storing the generated data tuples in a set of storages; and a data fetcher for retrieving the generated data tuples from the set of storages and passing each retrieved data tuple through the plurality of data processing stages, the data fetcher comprising the idle-signal injecting circuit and interspersing the idle signals among the data tuples passed through the data processing stages.
 7. The network interface device of claim 1, wherein each stage comprises a set of storage elements to store a first set of input values for the data processing stage during a first clock cycle, wherein when the data processing stage receives an idle signal for a subsequent second clock cycle, the data processing stage's set of storage elements does not store a second set of input values for the data processing stage during a second clock cycle but instead continues storing the first set of input values during the second clock cycle.
 8. The network interface device of claim 1, wherein each stage comprises: a set of storage elements to receive a clock signal and in response to the clock signal, to store a set of input values for the data processing stage during a clock cycle, and a clock gating circuit having a first input to receive the clock signal and a second input to receive a clock valid signal that (i) is active when the data processing stage receives a data tuple to process and (ii) is inactive when the data processing stage receives an idle signal, wherein when the clock valid signal is active during a first clock cycle, the clock gating circuit provides an active cycle of a clock signal to the set of storage elements to accept a new set of input values for storage during the first clock cycle; wherein when the clock valid signal is inactive during a second clock cycle, the clock gating circuit does not provide an active clock cycle of the clock signal to the set of storage elements during the second clock cycle, which prevents the set of storage elements and a plurality of other elements of the data processing stage from changing their operational states.
 9. The network interface device of claim 1, wherein a stage is to process data tuples by performing table lookup operations based on values stored in the data tuples, wherein when a data processing stage receives an idle signal during a particular clock cycle, the data processing stage does not perform table lookup operations during the particular clock cycle.
 10. The network interface device of claim 1, comprising circuitry to process data tuples associated with received data messages in order to forward the data messages to destination devices or to other forwarding elements in a network that serve as the next hops in a network for the data messages.
 11. The network interface device of claim 10, wherein processed data tuples are header values of the received data messages, wherein at least a subset of the plurality of data processing stages of the data-plane forwarding circuit perform match-action operations that attempt to match the header values with flow-based rules and that perform actions on the header values based on actions associated with matching flow-based rules, in order to forward the data messages to destination devices or to other forwarding elements in the network.
 12. A method for controlling power consumption of a data-plane forwarding circuit that processes data tuples associated with data messages received by the data-plane forwarding circuit, the data-plane forwarding circuit for configuration by a control-plane circuit, the method comprising: processing the data tuples in a plurality of data processing stages; receiving configuration data from the control-plane circuit; and based on the received configuration data, generating idle signals for the data processing stages to put each stage that receives an idle signal in an idle state to reduce power consumption of the data-plane circuit.
 13. The method of claim 12, wherein the configuration data specifies the frequency at which the idle-signal injecting circuit generates idle signals.
 14. The method of claim 12, wherein an idle signal traverses successively through several data processing stages.
 15. The method of claim 12 further comprising: generating data tuples from the received data messages and storing the generated data tuples in a set of storages; retrieving the generated data tuples from the set of storages and passing each retrieved data tuple through the plurality of data processing stages; and while retrieving and passing the data tuples, interspersing the idle signals among the data tuples passed through the data processing stages.
 16. A network forwarding element comprising: a data-plane forwarding circuit to process data tuples associated with data messages received by the forwarding element; and a control-plane circuit for configuring the data-plane forwarding circuit; said data-plane forwarding circuit comprising: a plurality of data processing stages to process the data tuples; and an idle-signal injecting circuit (i) to receive from the control-plane circuit configuration data, and (ii) based on the received configuration data, to generate idle signals for the data processing stages to put each stage that receives an idle signal in an idle state to reduce power consumption of the data-plane circuit.
 17. The network forwarding element of claim 16, wherein the data-plane forwarding circuit and the control plane circuit are part of a network forwarding element that comprises a power detecting circuit that identifies power consumption of the network forwarding element.
 18. The network forwarding element of claim 16, wherein the data-plane forwarding circuit and the control plane circuit are part of a network forwarding element that comprises a power detecting circuit that identifies power consumption of the data-plane forwarding circuit.
 19. The network forwarding element of claim 16, wherein an idle signal traverses successively through several data processing stages.
 20. The network forwarding element of claim 19, wherein the data-plane forwarding circuit further comprises: a parsing circuit for generating data tuples from the received data messages and storing the generated data tuples in a set of storages; and a data fetcher for retrieving the generated data tuples from the set of storages and passing each retrieved data tuple through the plurality of data processing stages, the data fetcher comprising the idle-signal injecting circuit and interspersing the idle signals among the data tuples through the data processing stages. 